Pinning Down Hookflash Timing

[markcosta]

Hi, first off - excellent tech support guys, having read this forum I can see you're much better than other software companies I've tried!

 

The problem I am having is with the latest release of VG for Dialogic (6.0.3165), my Dialogic D/-4PCI-U and our Samsung DCS816 PBX

 

I have found that the PBX expects a hookflash timing of between 80 and 120 ms (these are defined as the minimum and maximum values).

 

I've tried setting values between 7 and 25 for the value in the config.xml file and restarted Voiceguide before trying each value. The problem is that the PBX either thinks that my Dialogic card has hung up, or I hear the extension number's tones - i.e. the hookflash is too short.

 

Interestingly, I've been able to tie it down to this: a value of 19 is too short, but a value of 20 is too long??? Can you use 19.5? Surely this is being too precise?

 

I have an analogue phone that I've tried on one of the PBX's analog extensions and am able to hookflash with that with no problems. I've tried monitored, blind and announced transfers but still can't get the timing right. I have Release 6 Build 61 of Intel's Dialogic software and am running Windows 2003 SP1 up to date with Microsoft Update

 

I've enclosed a logfile with the hookflash set to 19. I'm all out of ideas please please help if you can!

 

Many thanks

Mark

1002vgm.txt

[SupportTeam]

Hi, first off - excellent tech support guys, having read this forum I can see you're much better than other software companies I've tried!

Thanks

 

Errors visible in the trace suggest that Windows Scripting is not installed on your system...

 

Which is a bit strange if the system has all the updates installed on it...

 

Please see: http://msdn.microsoft.com/downloads/list/webdev.asp

 

And download from there "Microsoft Windows Script 5.6 for Win2000/XP".

 

I have found that the PBX expects a hookflash timing of between 80 and 120 ms

The hookflash setting should be set to 10, to represent 100ms.

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

 

VoiceGuide=10

NumberLoader=0

VoicemailManager=0

EmailSender=0

TapiWrapOcx=10

SapiWrapOcx=0

Then restart VG and make a test call.

 

Debug Trace files will be created in VG's \log\ subdirectory.

 

Please .ZIP up and post the "tw" trace.

[markcosta]

Hi I've installed Windows Scripting and set the value at 10, rebooted and then run VoiceGuide as instructed.

 

The Hookflash was too short apparently as I heard the transfer tones.

 

Here's another trace

1003tw.txt

[SupportTeam]

Trace shows that the hookflash timing is successfully set to a value of 10 (representing 100ms):

 

153544.216 001 dlgc dx_setparm(1, DXBD_FLASHTM, &[10]) => 0,

 

and the timing in the trace when the hookflahs is issued is consistent with the hookflash lasting about 100ms:

 

153601.741 001 dx_dial(1,&) ok

153602.002 001 ev TDX_DIAL (Dial Completed)

 

I've been able to tie it down to this: a value of 19 is too short, but a value of 20 is too long???

That is very unusual.

 

Can you use 19.5? Surely this is being too precise?

No, you cannot use fractional settings. The DXBD_FLASHTM setting must be an integer.

 

Using Config.xml to set the DXBD_FLASHTM usually works, but another way to try is using the .PRM file.

Please make a system summary file using the sys_infoDNA.exe or its_sysinfo.exe program (see in directory: C:\Program Files\Dialogic\bin) and .ZIP up and post the resulting file.

(as described in: http://www.voiceguide.com/suppTechnicalSupp.htm).

This should let us identify which .PRM file you should be editing to hard set the hookflash timing value on Dialogic driver level.